@the-djmaze Perhaps we can have an option for admins like "Integrate nextcloud contacts fully"

• If that option is ticked, we disable snappymail PDO contacts and suggestions
• Along with that we disable the option in the right side menu

The UX will then be very similar to the attachments integration for nextcloud, where you can browse files in your cloud and attach them. Your contacts will be saved into your cloud and you can browse your contacts from your cloud app.

Hi,
I'm very happy to see that you've intention to work on this as this would make SnappyMail a lot better when working together with Nextcloud 🙂.
I would be happy to help testing this - when you're at a good point just let me know.

@the-djmaze What do you think about this change?

• Suggestions come from the plugin for contact suggestions and are handled separately in the main-fabrica hook anyway so no changes there
• Since IncFrec is the only function used to insert new contacts when an email is sent, I add logic only here to add/update into the cloud address book
• I choose a uri 'webmail' by default; maybe in the future we can implement as an option for users the choice of address book to save too
• To disable the contacts UI in snappymail, I add a new parameter called contactsExternal for frontend to understand if external provider or not and method called IsExternal for the address book to announce whether it is internal/external

@cm-schl

Hi,
sorry I tried to test you changes, but I don't get it to work on my test instance of Nextcloud. A question: what is the best way to get the changes to a working Nextcloud installation with SnappyMail installed? To patch the files manually seams wrong - there is surly a better way 🙂.

• Disabling the default contacts UI seams ok to me, but somehow the administrator has to be informed about this in the Adminpanel -> Contacts. Otherwise we would create a situation where an Admin sets the flag to activate the contacts UI there and then the Nextcloud plugin overwrites this setting.

• There should surly exist a option to let the user / admin choose where the contacts get saved. For example a company could use Thunderbird on their computers with for example the addon Cardbook. There you can choose an address book where new contacts should be saved. Therefore also SnappyMail in such a situation would have to use the same address book for this...

I will come back later to this. 😉

I would love to have this as well. Any solution yet? Let me know if del is needed, testing, dev, anything.

@stepcellwolf I do get back to you, got a bit busy in between.

I mostly need some dev to deal with the points raised by @cm-schl in #1227 (comment)

• Mainly, let the admin know that this one overrides the main contacts UI and
• Let the user choose the addressbook from the list of addressbooks in cloud

and ofc some testing..

A good example of multiple address books is the people around you.
You ask a friend/colleague/etc. for someone his contact details, and they transfer the data to you and you put it in an address book.

Your phone only has "contacts" and you categorize them by any tag needed (family, friends, coworker, client, etc.)
The need for multiple address books is there, and there's not. Because some people are family & coworker or friend & client.

The biggest issue is GDPR where client data should not leave the building and yet, it is on your phone 😛

To support multiple address books, SnappyMail needs some big changes.
Currently i don't see the benefit vs all coding hours to get something nice.

Maybe someone already has a very bright idea?

To support multiple address books, SnappyMail needs some big changes.
Currently i don't see the benefit vs all coding hours to get something nice.

@the-djmaze We can continue with a single address book but allow nextcloud admins to choose which one to activate(the SnappyMail one or full integration with nextcloud), wdyt?

I have already deployed a patched version if this PR to servers with a good amount of usage and this address book does over-ride the pdo address book of SnappyMail correctly.

@the-djmaze We can continue with a single address book but allow nextcloud admins to choose which one to activate(the SnappyMail one or full integration with nextcloud), wdyt?

I too don't see it necessary to support multiple address books 👍.
Having the possibility to choose the destination of "collected addresses" would perfectly integrate into Nextcloud because there is also a automatically generated address book called "last contacted". As said for company use the option to choose the destination would be crucial when having different mail clients following the same logic (saving the new addresses into a specific address book).

Talking from a company perspective I would have to add something: for single users a simple dialog to choose the destination for new contacts would be enough. For an administrator it would be nice to have the possibility to preset this destination address book for all users.
Example: in Thunderbird you can preset this by MCD by a string like "https://<SERVER>/remote.php/dav/addressbooks/users/" + getenv("USERNAME") + "/<ADDRESS_BOOK_NAME>/".
It may be to much at the moment, but i definitely see a use case for larger installs 🙂. Maybe some provider would like to add SnappyMail to its Nextcloud for all users. Then a definition for a default destination would prevent to mess up the "normal" address book of the users with collected addresses...

@the-djmaze @akhil1508 this is ready to be reviewed.

@the-djmaze So we have the following functionality now:

1. Setting for user to choose their addressbook
2. Settings for admins to set:

• Default addressbook uri
• Default Addressbook description
• Disable inbuilt contacts UI so users can use nextcloud contacts
• Enable NC addressbook so users' contacts can save to NC contacts

3. Save contact to NC addressbook on send if it is not a new contact (no duplicates)

cc @fahim44

I'm looking forward to this feature

It will actually be very good, I would like to ask how it will be in the case of two or more accounts authenticated in Snappymail, will this create the contacts in the same addressbook?

Or will it save in each user's addressbook?

I'm looking forward to this feature

It will actually be very good, I would like to ask how it will be in the case of two or more accounts authenticated in Snappymail, will this create the contacts in the same addressbook?

Or will it save in each user's addressbook?

@mstolf the contacts will be saved in the nextcloud addressbook. By default, all contacts will be saved in the default addressbook defined by nextcloud admin. But, this feature support addressbook switching for each snappyMail account. So, if you have nextcloud account with multiple addressbooks, & multiple snappyMail account setup, you can pick separate addressbooks for each snappyMail account

screenshot:

Hi,
first of all thanks for your work on this!

As promised before some feedback from my first tests:

1. I first did not understood that you have to activate the "contacts" in the SnappyMail configuration. Without this no contact gets saved even if inside the configuration of the Nextcloud plugin something is configured. I don't know if other users would fail in the same way or if its only me 🙂.
2. defaultNCAddressbookUri and defaultNCAddressbookName: I was able to use the plugin, but to me first it wasn't really clear what to put there. Why defaultNCAddressbookUri and defaultNCAddressbookName is necessary? Wouldn't only defaultNCAddressbookUri be sufficient to identify the address book?
3. Where does defaultNCAddressbookDescription gets written to when a contact is saved?
4. disableSnappymailContactsUI: In my tests i did not saw a difference between activating and deactivating this... Only the original setting (see point 1) did had an impact on the ui...
5. As admin I would prefer to set the address book where all addresses should get saved without giving the user to change my preset. At the moment, when I set defaultNCAddressbookUri and defaultNCAddressbookName and disable enableNcAddressbook the contact does not get saved... So at the moment it seams that enableNcAddressbook does not only disables the user from choosing the address book but disables the whole functionality. This wasn't clear to me because i didn't saw a connection between the various options. It would be nice if this settings would be grouped together to enable the user to understand that these are connected (and not usable independently)... But this maybe is only my preference 🙂.
   Example from my plugin (https://github.com/the-djmaze/snappymail/tree/master/plugins/ldap-mail-accounts):

Hi @cm-schl , let me try to answer your questions

1. We want to save contacts into nextcloud addressbook. I think this make more sense to save contacts, we need to enable the contacts first. Else it makes more confusion & will feel like snappyMail not working.

2 & 3. This patch will try to create new nextcloud addressbook / reuse if already present (search against addressbook uri). This is because we need addressbook to save our contacts & admin can't be sure user has any specific / any addressbook present or not by default. User can change it later as per his preference. To create a nextcloud addressbook, we need uri, name, & description. defaultNCAddressbookUri, defaultNCAddressbookName, defaultNCAddressbookDescription serves those perposes.

4. disableSnappymailContactsUI disable snappyMail specific contact UI elements. This is present so admin can hide snappyMail contacts entry option to avoid confusion (as contacts will be automatically saved to nextcloud addressbook).

disableSnappymailContactsUI = false	disableSnappymailContactsUI = true

5. enableNcAddressbook is the main switch which will enable this feature. We want this feature to be optional, so admin can choose whatever he wants it or not. If you enable enableNcAddressbook, then defaultNCAddressbookUri & defaultNCAddressbookName, defaultNCAddressbookDescription will be taken as consideration to create/use nextcloud addressbook. disableSnappymailContactsUI is used to disable snappyMail inhouse contacts UI elements to avoid confusion.

Hi @fahim44 and thanks for your response!
1 & 2 & 3 & 4: makes completely sense like you described it. Maybe this information could get added to the readme? (I like documentation 😉🙂).

5: like you and I said enableNcAddressbook disables everything. It may only be me but I first thought that the description Enable User to choose Nextcloud addressbook for recipients would let the admin choose if the user can choose the address book by himself or only the admin can do this by setting the fields below. Therefore a "Enable" checkbox or some grouping came into my mind. I thought that this maybe makes it clear that disabling the first option would disable everything and not only the possibility to let the user choose.

Hi @fahim44 and thanks for your response! 1 & 2 & 3 & 4: makes completely sense like you described it. Maybe this information could get added to the readme? (I like documentation 😉🙂).

5: like you and I said enableNcAddressbook disables everything. It may only be me but I first thought that the description Enable User to choose Nextcloud addressbook for recipients would let the admin choose if the user can choose the address book by himself or only the admin can do this by setting the fields below. Therefore a "Enable" checkbox or some grouping came into my mind. I thought that this maybe makes it clear that disabling the first option would disable everything and not only the possibility to let the user choose.

updated README. cc @cm-schl

Hi @the-djmaze ! Can you give a look? TIA :)

This work looks FANTASTIC

Hi @the-djmaze ! Can you give a look? TIA :)

Will look at it. Just had some other things to do ;)